Good catch! I will test it out myself as well and think about it. I'd like if it we didn't have to explicitly handle this, but we'll see. Might take me a day or two to look at this more deeply.

Thanks, that sounds good, it would definitely be preferable to not have this code in the project!

Actually, my initial thought with this was just to set the initialState of routerReducer.path to locationString(window.location) when running in a browser. For some reason that eludes me now I decided it wouldn't work, but having thought about it some more it seems like it would work OK:

const initialState = typeof window === undefined ? {} : {
  path: locationToString(window.location)
};

@ellbee oh, good point! I don't see any problem with that. Can you test it and see if it works, and possibly update this PR? If not I can get to it this week.

Sure, I'll have some time to look at it later today.

I've updated the PR. It is working fine in the tests I have done.

Looks good, thanks!